Skip to content

Restore native Runtime package CI portability - #820

Merged
wieslawsoltes merged 1 commit into
mainfrom
fix/runtime-ci-bootstrap-819
Sep 20, 2026
Merged

wieslawsoltes merged 1 commit into
mainfrom
fix/runtime-ci-bootstrap-819

Conversation

@wieslawsoltes

Copy link
Copy Markdown
Collaborator

Problem

Current main could not produce native Runtime packages because the final editor-platform V8 bootstrap literal exceeded the deliberate MSVC portability ceiling. The general CI Windows Dawn fixture also omitted the already required exact D3D12 bridge export. Wiring the dormant bootstrap regression into the producer preflight exposed the same latent limit violation in the Service Worker bootstrap.

Change

  • split the two oversized raw literals through their existing ordered source-part concatenation paths
  • keep both JavaScript programs byte-identical to current main
  • update the Windows Dawn fixture with websceneDawnQueryD3D12DeviceV1
  • run the bootstrap portability regression before RID package builds
  • document the exact failed runs and release dependency

Focused validation

  • 8/8 bootstrap portability and Dawn export tests pass
  • generated editor bootstrap passes node syntax checking
  • editor program remains 66,119 bytes with SHA-256 c2d16b1d6c4f30c18a84ae6a4264c14713dd65670c00a129ab97510a5ec74bd9
  • Service Worker program remains 33,683 bytes with SHA-256 d1cf09515113ae5aea8a2b772822aa1b3d3533c1c29d15a2ee6f2c34558210f0
  • largest resulting parts are 14,473 and 7,817 bytes, both below 15,000

Closes #819

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Repair current-main native Runtime CI bootstrap and Dawn fixtures

1 participant